Low-power mobile telephony alert system

ABSTRACT

A low-power mobile telephony alert system and an alert device. The alert device has a communication interface configured to establish a low-power communication link with a mobile device for transmitting status data to the mobile device, and a telephony-enabled communication linked with the mobile device for initiating telephony from the mobile device while in locked mode. The alert device can initiate a status check request to third party contact devices before escalating to connect to the mobile device from locked mode to initiate telephony to an emergency service. The alert device is compact and can be incorporated into an article of jewelry or a wearable loop member.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. 62/402,190, filed Sep. 30,2016, the entirety of which is incorporated herein by reference.

FIELD

The present disclosure relates generally to alert systems, and inparticular to mobile telephony alert systems.

BACKGROUND

Alert systems, including personal emergency response systems, and thelike, provide individuals with a means for obtaining assistance in timesof need. There is particularly a need for mobile alert systems forindividuals who work in remote areas, or who work alone in precariouswork environments, so that such individuals can call for assistanceremotely when in distress. Elderly or infirm individuals may havesimilar needs.

Although many individuals store everyday mobile devices such as smartphones, tablets, and other communication devices on their persons, suchmobile devices are often inaccessible to an individual in dire times ofneed. Thus, an alert system typically includes a dedicated alert devicestored on an individual's person with a button which, when operated intimes of distress, provides means for putting the individual incommunication with an emergency dispatch service.

Although some everyday mobile devices stored on a person includetelephony capability, such devices are often restricted from initiatingtelephony when in locked mode. Thus, many implementations of existingalert systems comprise two units: a mobile alert device, and astationary base unit for providing telephony service. A distressedindividual can activate the mobile alert device, which causes astationary base, typically stored in a home, to make a telephoneconnection with a dispatch service. The individual may then speakthrough the alert device, cause speech to be transmitted through thebase unit, through a telephone system, and ultimately to a dispatchservice. A limitation of such an alert system is that its functionalityis limited by the operating range of the connection between the mobilealert device and the stationary base unit. Furthermore, the necessity ofthe additional hardware to allow for speech from the mobile alert devicemakes the mobile alert device cumbersome.

Other alert systems seek to overcome the deficiencies of the limitedrange and mobility of alert devices relying on a stationary base unit byproviding all of the communication hardware that was once stored in boththe base unit and the alert device in a single device. Such devices areoften bulky, highly noticeable and obtrusive.

A further limitation of the previously mentioned alert systems is thatthe distressed individual can generally only be put in communicationwith an emergency dispatch service, with no less drastic alternative forsituations where an emergency dispatch service is not appropriate. Anindividual may find oneself in a distressful situation requiringassistance, but may not be willing to go to the drastic length ofcalling upon an emergency dispatch service, and therefore may decideagainst using such an alert system at all.

SUMMARY

The present disclosure relates to a low-power mobile telephony alertsystem. The present disclosure sets forth an alert device that includesa communication interface configured to establish a low-powercommunication link with a mobile device for transmitting status data tothe mobile device, and a telephony-enabled communication link with themobile device for initiating telephony from the mobile device while inlocked mode. The alert device can initiate a status check request tothird party contact devices before escalating to initiate telephony toan emergency service. The alert device is compact and can beincorporated into an article of jewelry or a wearable loop member.

According to an aspect of the disclosure, a low-power mobile telephonyalert system is provided. The system includes a mobile device, at leastone third party contact device, an emergency service, and an alertdevice for initiating telephony from the mobile device in locked mode tothe emergency service.

According to an aspect of the disclosure, an alert device for initiatingtelephony from a mobile device in locked mode includes a communicationinterface. The communication interface is configured to establish afirst paired connection with the mobile device, the mobile devicerunning a status data monitoring application, the first pairedconnection includes a low-power communication link having privilegedaccess to the status data monitoring application for recording statusdata from the alert device to the mobile device in locked mode, thelow-power communication link configured for continuous low-energytransmission of status data from the alert device to the status datamonitoring application, to establish a second paired connection with themobile device, the second paired connection includes a telephony-enabledcommunication link having privileged access to initiate telephony fromthe mobile device in locked mode, the telephony-enabled communicationlink configured for initiating telephony from the mobile device inresponse to recognition of a trigger represented in the status data fromthe alert device, and to transmit the status data from the alert deviceto the mobile device, via the first paired connection, for collection bythe status data monitoring application. The alert device includes amemory storage unit for storing programming instructions and the statusdata, and a processor in communication with the communication interfaceand memory storage unit. The processor is configured to recognize atrigger represented in the status data, and, responsive to recognitionof the trigger, initiate, via one of the first paired connection and thesecond paired connection, a status check request from the mobile deviceto at least one third party contact device, the status check requesthaving an expiry rule, identify satisfaction of the expiry rule of thestatus check request, and, responsive to satisfaction of the expiryrule, connect to the mobile device from locked mode via the secondpaired connection; and initiate, via the second paired connection,telephony from the mobile device to a third-party emergency service.

The communication interface may include a dual-mode module configured toestablish the first paired connection and the second paired connection.

The alert device may further include a motion sensor, wherein the statusdata includes motion sensor data, and wherein the trigger includes thestatus data indicating inactivity of the alert device for apre-determined length of time.

The alert device may further include a motion sensor, wherein the statusdata includes motion sensor data, and wherein the trigger includes thestatus data indicating a disturbance in the motion sensor data.

The alert device may further include an alert button, and wherein thetrigger includes the status data indicating a pressed state of the alertbutton.

The alert device may include a wearable article having an opening forproviding concealed access to the alert button of the alert device.

The wearable article may include a fascia portion and a pendant portionreleasably attachable to enclose the alert device, the fascia portionproviding ornamentation to the alert device, and the pendant portionconcealing the alert button and providing a loop for wearing the alertdevice.

The expiry rule may include lapsation of a countdown timer.

According to another aspect of the disclosure, a method for initiatingtelephony from a mobile device in locked mode using an alert deviceincludes pairing the alert device with the mobile device via a firstpaired connection, the mobile device running a status data monitoringapplication, the first paired connection includes a low-powercommunication link having privileged access to the status datamonitoring application for recording status data from the alert deviceto the mobile device in locked mode, the low-power communication linkconfigured for continuous low-energy transmission of status data fromthe alert device to the status data monitoring application, pairing thealert device with the mobile device via a second paired connection, thesecond paired connection includes a telephony-enabled communication linkhaving privileged access to initiate telephony from the mobile device inlocked mode, the telephony-enabled communication link configured forinitiating telephony from the mobile device in response to recognitionof a trigger represented in the status data from the alert device,transmitting status data from the alert device to the mobile device, viathe first paired connection, for collection by the status datamonitoring application, responsive to recognition of the triggerrepresented in the status data, initiating, via one of the first pairedconnection and the second paired connection, a status check request fromthe mobile device to at least one third party contact device, the statuscheck request having an expiry rule, responsive to satisfaction of theexpiry rule of the status check request, connecting to the mobile devicefrom locked mode via the second paired connection, and initiating, viathe second paired connection, telephony from the mobile device to athird-party emergency service.

Pairing the alert device with the mobile device via a second pairedconnection may involve generating a link key to be stored on the alertdevice and mobile device to authenticate the second paired connection.

The expiry rule may include lapsation of a countdown timer.

The status data may include motion sensor data from a motion sensor onthe alert device, and wherein recognition of the trigger represented inthe status data involves recognizing inactivity of the alert device fora pre-determined length of time.

The status data may include motion sensor data from a motion sensor onthe alert device, and wherein recognition of the trigger represented inthe status data involves recognizing a disturbance in the motion sensordata.

The status data may include pressed state data from an alert button onthe alert device, and wherein recognition of the trigger represented inthe status data includes a pressed state of the alert button.

Other features and advantages of the system and alert device aredescribed more fully below.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments will now be described, by way of example only,with reference to the attached Figures, wherein:

FIG. 1 is a schematic diagram of mobile telephony alert system includingan alert device and a mobile device stored on a person;

FIG. 2 is a block diagram of the components of the alert device of thesystem of FIG. 1;

FIG. 3 is a perspective view of the alert device of the system of FIG. 1showing the rear chassis of the alert device;

FIG. 4 depicts a screen capture of a status data monitoring applicationrunning on the mobile device of FIG. 1;

FIG. 5A is a flowchart of a method for establishing telephony-enabled,low-power monitoring of the alert device of the system of FIG. 1;

FIG. 5B is a flowchart of a method for alerting third parties ofdistress from the mobile device of FIG. 1 in locked mode;

FIG. 6 depicts the mobile device of FIG. 1 making a status check requestto a third-party contact device;

FIG. 7A is an assembly diagram of the alert device of FIG. 1 assembledinto an article of jewelry;

FIG. 7B is an assembly diagram of the alert device of FIG. 1 assembledinto a wearable loop member;

FIG. 8 provides additional views of the alert device of FIG. 1;

FIG. 9 provides additional views of the article of jewelry of FIG. 7A;

FIG. 10 provides additional views of the alert device of FIG. 1assembled into the article of jewelry of FIG. 7A; and

FIG. 11 provides additional views of the wearable loop member of FIG.7B.

DETAILED DESCRIPTION

The present disclosure relates to a low-power mobile telephony alertsystem. The system includes an alert device to be worn or carried by anindividual. The alert device is in communication with a mobile device,such as a smartphone other mobile communication device having telephonycapability, also carried by the individual. When a trigger indicatingthat the individual is distressed is recognized, the alert device cancause the mobile device to initiate a status check request to thirdparty contact devices, and can initiate telephony from the mobile deviceto an emergency service.

The alert device uses a low-power communication link to transmit statusdata from the alert device to the mobile device. The status data caninclude, for example, motion sensor data, battery data, heartrate, bloodpressure, or other physiological data, or button press data, which mayindicate whether the wearer of the alert device is in distress. Thelow-power communication link is generally continuously active to be usedfor monitoring purposes.

Many mobile devices, however, restrict the ability for low-powercommunication links to initiate telephony while the mobile device is inlocked mode. For security reasons, it may be desirable for mobiledevices to restrict telephony from continuously-active communicationlinks while the mobile device is in locked mode. Thus, low-powercommunication links are not reliable for initiating telephony on some ofsuch restricted mobile devices.

The alert device therefore uses a telephony-enabled communication linkto use the telephony capability of the mobile device while the mobiledevice is in locked mode, thereby overcoming such restrictions againstlow-power communication links. The telephony-enabled communication linkis made active only where a trigger is detected from the status datatransmitted by the alert device. For example, the telephony-enabledcommunication link is activated when the status data indicates that anemergency button has been pressed on the alert device.

Thus, the alert device maintains a low-power communication link with themobile device that is generally continuously active for monitoringpurposes, and the alert device can activate a telephony-enabledcommunication link to initiate telephony to make an emergency call whilethe mobile device is in locked mode. Thus, an alert device whichleverages the telephony capability of the mobile device and obviates theneed for telephony hardware on the alert device is provided.Furthermore, the alert device can initiate status check requests fromthe mobile device to third party contact devices as a less drastic formcalling for distress before initiating telephony to an emergencyservice. Further still, the alert device can be made compact andincorporated into an article of jewelry or a wearable loop member fordiscrete wear.

Non-limiting embodiments of the system and the alert device arepresented in the following Figures. For convenience, reference numeralsmay be repeated (with or without an offset) to indicate analogouscomponents or features.

FIG. 1 is a schematic diagram depicting a mobile telephony alert system50, according to a non-limiting embodiment. The system 50 includes analert device 100 to be stored on an individual's person, and a mobiledevice 200 to be stored on an individual's person or nearby. The system50 further includes a network 60, one or more third party contactdevices 70, and one or more emergency services 62.

The mobile device 200 is in communication with one or more third partycontact devices 70, and one or more emergency service 62, via one ormore computers or telecommunications networks, shown as network 60,which can include a wireless cellular data network, a Wi-Fi network, alocal-area network, a wide-area network (WAN), a Bluetooth pairing orconnection, the internet, a virtual private network (VPN), a combinationof such, and similar.

In the present embodiment, the mobile device 200 includes a smart phonerunning an operating system such as, for example, Android®, iOS®,Windows® mobile, BB 10, or similar. In other embodiments, the mobiledevice 200 includes a tablet computer, a personal digital assistant(PDA), laptop, or other mobile computing device with telecommunicationscapability.

In the present embodiment, the contact device 70 similarly includes asmart phone running an operating system such as, for example, Android®,iOS®, Windows® mobile, BB 10, or similar. In other embodiments, thecontact device 70 includes a tablet computer, a personal digitalassistant (PDA), laptop, or other mobile computing device withtelecommunications capability.

In the present embodiment, emergency service 62 includes a third partyemergency service having telecommunications means for coordinatingemergency response teams. However, in other embodiments, emergencyservice 62 may include an emergency dispatch service.

The alert device 100 is in communication with the mobile device 200 viaa first paired connection 151. The first paired connection 151 includesa low-power communication link configured for generally continuouslow-energy transmission of status data 153 from the alert device 100 tothe mobile device 200. In some embodiments, the first paired connection151 includes a Bluetooth Low Energy (BLE) connection. In suchembodiments, the alert device 100 may be the peripheral device and themobile device 200 may be the central device.

The alert device 100 is also in communication with the mobile device 200via a second paired connection 152. The second paired connection 152includes a telephony-enabled communication link having privileged accessto initiate telephony from the mobile device 200 in locked mode. In someembodiments, the second paired connection 152 includes a BluetoothClassic (BTC) connection. In such embodiments, the alert device 100 isthe master in the master-slave BTC connection, and the second pairedconnection 152 includes a hands-free profile (HFP) providing privilegedaccess for initiation of telephony. As part of the pairing process ofestablishing the second paired connection 152, a link key 162 is storedby both the alert device 100 and the mobile device 200 forauthenticating the paired connection.

The mobile device 200 is loaded with status data monitoring application202, running as software, and each contact device 70 is similarly loadedwith status data monitoring application 202, running as software, forfacilitating communication, and for collection of status data 153transmitted from the alert device 100. Status data 153 is also collectedby application 202 and recorded in mobile device 200 for later use, andin the present embodiment, is similarly recorded on contact device 70for monitoring by a third party contact. In the present embodiment, themobile device 200 and contact devices 70 each run the same application202, which may be configured to operate for the distinct role of themobile device 200 or the contact device 70, as discussed below withreference to FIGS. 4-6. In other embodiments, however, the contactdevices 70 may run distinct software applications, and status data 153may not be recorded on a contact device 70 for monitoring, provided thecontact devices 70 can still receive status check requests and havetelephony capability, as described below.

The alert device 100 is loaded with firmware 160, which controlstransmission of status data 153 from the alert device 100 to mobiledevice 200 via first paired connection 151. Firmware 160 furthercontrols detection of triggers which may indicate the wearer of thealert device 100 is in distress, and for initiating status requestchecks and telephony from mobile device 200, as discussed below withreference to FIGS. 4-6.

FIG. 2 is a block diagram of the components of the alert device 100,according to a non-limiting embodiment. In the present embodiment, thealert device 100 includes a processor 120 which communicates with acommunication interface 130.

In the present embodiment, the processor 120 includes a microcontrollerwith a floating-point unit (FPU), an integrated circuit, a serialperipheral interface, and a general purpose I/O utilizing pulse-widthmodulation. However, in other embodiments, the computation of processor120 may be achieved by other means, such as, for example, a statemachine, a logic gate array, an application-specific integrated circuit(ASIC), a system-on-a-chip (SOC), a field-programmable gate array(FPGA), or similar, capable of executing, whether by software, hardware,firmware, or a combination of such, to carry out the methods discussedin greater detail below.

In embodiments where the first paired connection 151 and second pairedconnection 152 comprise BLE and BTC connections respectively, thecommunication interface 130 includes at least one Bluetooth modulecapable of establishing a hands-free profile for initiating telephony.

In the present embodiment, the communication interface 130 includes adual-mode BLE/BTC module, such as a CC2564B Dual-mode Bluetoothcontroller, or a STM32F4 (ST) microcontroller unit. In otherembodiments, however, communication interface 130 may comprise separateBLE and BTC modules.

The processor 120 also communicates with motion sensor 103 and motorvibrator 105. The motion sensor 103 may comprise an accelerometer orgyroscope or a combination of such or similar, to gather data about themotion of alert device 100 as part of status data 153. Disturbances orlengthy pauses in motion data may indicate a trigger that the wearer ofthe alert device 100 is in distressed, as discussed in greater detailbelow. The motor vibrator 105 can provide haptic feedback to theindividual to indicate that the alert button 102 has been pressed, orthat battery power is low, for example.

The alert device 100 further includes a power supply 107, such as abattery, which is charged via charging port 104. In other embodimentswhere power supply 107 includes a battery, power supply 107 may becharged via kinetic energy harvester means, solar cells, or may besubstituted for an external power source, such as a power connectionwith the mobile device 200, an AC or DC connection, or otherwise.

The processor 120 further communicates with alert button 102, visualindicators 108, and reset button 106. Activation of the alert button 102by the wearer may indicate a trigger that the wearer of the alert device100 is in distressed, as discussed in greater detail below.

Thus, in the present embodiment, status data 153 includes motion sensordata collected from motion sensor 103, the battery life of power supply107, a pressed (or unpressed) state of alert button 102, and the signalstrengths of paired connections 151, 152, from communication interface130, which may serve as an analog for the distance from alert device 100to mobile device 200. In other embodiments in which other sensors areonboard alert device 100, additional information related to the state ofalert device 100 may be included in status data 153. For example, thealert device 100 may include a microphone or other sound recorder (notshown), and sound data may be included in status data 153. As anotherexample, alert device 100 may include a heartrate monitor (not shown),and heartrate data may be included in status data 153. Similarly, wherethe alert device 100 may include a blood pressure sensor, and bloodpressure data may be included in status data 153.

Visual indicator 108 communicates state information about the alertdevice 100 to the wearer. In the present embodiment, visual indicator108 built into alert button 102 and is located beneath a translucentlayer 109 above the alert button 102. In the present embodiment, thevisual indicator 108 includes several tri-colour LEDs. In otherembodiments, state information can be communicated to an individual viaa single LED, a multi-colour LED, a series of LEDs, a speaker, motorvibrator 105, or otherwise.

The factory reset button 106 can be used to reset the alert device 100to factory settings.

The alert device 100 further includes a memory storage unit 125 havingfirmware 160 and in communication with processor 120 to configureprocessor 120 to carry out the methods discussed in greater detailbelow. In brief, firmware 160 which controls transmission of status data153 from the alert device 100 to mobile device 200 via first pairedconnection 151. Firmware 160 further controls detection of triggerswhich may indicate the wearer of the alert device 100 is in distress,and for initiating status request checks and telephony from mobiledevice 200, as discussed below with reference to FIGS. 4-6. In thepresent embodiment, status data 153 is stored on memory storage unit 125temporarily before being transmitted to mobile device 200. In someembodiments, status data 153 may be stored in memory storage unit 125for a short period of time before status data 153 is transmitted tomobile device 200. However, in other embodiments, status data 153 may bestreamed directly to mobile device 200 without prolonged storage onmemory storage unit 125.

FIG. 3 is a perspective view of the alert device 100, according to anon-limiting embodiment. FIG. 3 illustrates the peripheral components,including the alert button 102 having translucent layer 109, the wiredcharging port 104, reset button 106 and visual indicator 108. The alertdevice 100 further includes rear chassis 110 featuring the peripheralcomponents of the alert device 100, and front chassis 112 opposite therear chassis 110. The rear chassis 110 and front chassis 112 are shapedto fit into a piece of jewelry or other article, as described withreference to FIGS. 7A and 7B below, for discreet storage on anindividual's person. The alert button 102 is depressed into the rearchassis 110 to inhibit accidental pressing.

FIG. 4 depicts a screen capture of application 202 running on a contactdevice 70, according to a non-limiting embodiment. The contact device 70receives status data from a mobile device 200 across network 60 formonitoring by the contact device 70.

The application 202 includes a user interface 202A having a devicesbutton 204, a contacts button 206, a dashboard button 208, and a profilebutton 210. The screen capture shown in FIG. 4 indicates an activedashboard page 208A, which a user may select by pressing dashboardbutton 208.

The dashboard page 208A includes an identifier 208A-1 for indicating thewearer of the alert device 100 being monitored. The dashboard page 208Afurther includes panels or icons for displaying indications of statusdata 153, including an alert panel 208A-2, a motion panel 208A-3, abattery life icon 208A-4, and a connectivity icon 208A-5. The alertpanel 208A-2 can indicate whether an active alert caused by a trigger inthe status data 153 is present. The motion panel 208A-3 can indicatewhen motion data from the motion sensor 103 last indicated that thewearer of the alert device 100 moved, and may indicate whether asignificant disturbance (e.g. a fall) was detected by the motion sensor103. Battery life icon 208A-4 indicates the remaining battery life ofthe alert device 100. Connectivity icon 208A-5 indicates whether thealert device 100 is connected by paired connections 151, 152, in thepresent embodiment a BLE and BTC connection respectively, to thewearer's mobile device 200.

By pressing the devices button 204, a user may access a devices page(not shown), which allows a user to view an inventory of alert devices100 which contact device 70 is monitoring.

By pressing the contacts button 206, a user may access a contacts page(not shown). When accessed from a mobile device 200, the contacts pageindicates a list of third party contacts having contact devices 70. Auser of a mobile device 200 may then select various options such aswhich contact devices 70 will receive status check requests, asdiscussed below. or which contact devices 70 will receive a telephonecall. When accessed from a contact device 70, the contacts pageindicates a list of wearers of alert devices 100 being monitored, forwhom the contact device 70 will be alerted if an alert is triggered.

By pressing profile button 210, a user may access a profile page (notshown), which allows a user to adjust personal preferences of theapplication 202 and the like.

It is emphasized that interface 202A is shown as an example only. Thepanels and icons may be rearranged, and some pages may be omittedentirely, provided the application 202 can be used to monitor statusdata 153 and perform the functions of the methods described herein.Where application 202 is running on a contact device 70, for example,the devices page may be omitted. As a further example, when application202 is running on a contact device 70, the contacts page may be omittedin place of a plurality of dashboard pages 208A between which a user mayswitch.

In some embodiments, a mobile device 200 may transmit its location data,determined via global positioning systems (GPS), Wi-Fi locationtracking, or other location tracking systems, to a contact device 70.Thus, where a contact device 70 is alerted that the wearer of alertdevice 100 is in distress, the user of contact device 70 may verify thelocation of the wearer of the alert device 100 for rendering assistance.

FIG. 5A is a flowchart of a method 300 for establishingtelephony-enabled, low-power monitoring of an alert device 100,according to a non-limiting embodiment. The method 300 is described asperformed by a system and device discussed herein, but this is notlimiting and the method can alternatively be performed by other systemsand/or devices. It is to be emphasized that the blocks of method 300need not be performed in the exact sequence as shown.

At block 302, the mobile device 200 connects with the alert device 100to establish first paired connection 151. As discussed above, the firstpaired connection 151 includes a low-power communication link configuredfor generally continuous low-energy transmission of status data 153 fromthe alert device 100 to the mobile device 200. In some embodiments, thefirst paired connection 151 includes a Bluetooth Low Energy (BLE)connection. In such embodiments, the alert device 100 is the peripheraldevice advertising the BLE connection and the mobile device 200 is thecentral device.

At block 304, mobile device 200 connects with the alert device 100 toestablish first paired connection 151, the mobile device 200 is promptedby application 202 to pair the alert device 100 with the mobile device200 via second paired connection 152. In an example embodiment in whichthe mobile device 200 is an iOS device and the second paired connection152 includes a BTC connection, the mobile device 200 prompts the user toestablish the BTC connection.

At block 306, the alert device 100 is paired with the mobile device 200via second paired connection 152. As discussed above, the second pairedconnection 152 includes a telephony-enabled communication link havingprivileged access to initiate telephony from the mobile device 200 inlocked mode. In the present embodiment, the second paired connection 152includes a Bluetooth Classic (BTC) connection, and the alert device 100is the master in the master-slave BTC connection, and the second pairedconnection 152 includes a hands-free profile (HFP) enabling initiationof telephony. As part of the pairing process of establishing the secondpaired connection 152, a handshake occurs where a link key 162 isgenerated and stored by both the alert device 100 and the mobile device200 for authenticating the paired connection.

At block 308, status data 153 is transmitted from alert device 100 tomobile device 200 via first paired connection 151. As a low-powerconnection, status data 153 can be transmitted with low energy costs ona regular basis without undue drain on battery power of the alert device100 or mobile device 200.

When an individual is determined to be in distress, whether by thestatus data 153 including information regarding the pressed state ofalert button 102 indicating that the alert button 102 has been pressed,that the wearer of the alert device 100 has not moved for apre-determined period of time, that the wearer may have experienced afall, or another trigger apparent from status data 153 and recognized byfirmware 160 on alert device 100 as a trigger, a method for alertingthird parties is initiated, as discussed with respect to FIG. 5B below.

FIG. 5B is a flowchart of a method 400 for alerting third parties ofdistress from the mobile device 200 in locked mode, according to anon-limiting embodiment. The method 400 is described as performed by asystem and device discussed herein, but this is not limiting and themethod can alternatively be performed by other systems and/or devices.

Generally, the alert device 100 causes the mobile device 200 to sendstatus check request to a plurality of the individual's contact devices70 as a push notification launched by the application 202 running oncontact device 70. The status check request invites select personalcontacts to respond to the request by calling the distressed individualat the mobile device 200. The application 202 running on the mobiledevice 200, and the application 202 running on the contact device 70,can be associated such that the contact device 70 contains the telephonenumber of the mobile device 200 to call when so requested.

A telephone connection through network 60 puts the wearer of the alertdevice 100 in contact with the contact device 70 through telephony ofthe mobile device 200 so that assistance may be rendered.

If no personal contact having a contact device 70 responds within apre-determined length of time, then the alert device 100 uses the secondpaired connection 152 to cause the mobile device 200 to call anemergency service 62. The wearer of the alert device 100 can thencommunicate through the mobile device 200 to obtain emergencyassistance.

At block 402, a trigger is recognized in the status data 153 sent fromthe alert device 100 to the mobile device 200. A trigger may include anindication that the alert button 102 has been pressed, that the wearerof the alert device 100 has reported inactivity of the alert device 100for a pre-determined length of time, that the wearer may haveexperienced a fall, or another trigger apparent from status data 153 andrecognized by firmware 160 on alert device 100 as a trigger. Forexample, recognition that the alert device 100 has not reported movementby motion sensor data from motion sensor 103 in one hour may be atrigger indicating that the wearer of the alert device 100 is likely indistress. In other embodiments, a disturbance in motion sensor data frommotion sensor 103, such as that indicating a fall, can indicate theindividual is likely in distress.

Where motion sensor data from motion sensor 103 is monitored fortriggers, motion data that is sent to the mobile device 200 may beperiodically sent to contact devices 70 so that a personal contact maymonitor the individual's level of activity.

To save battery life, motion sensor data from motion sensor 103 may betransmitted to mobile device 200 in periodic batches. For example,motion sensor data may be transmitted only about every 180 seconds.

At block 404, after recognition of a trigger, a status check request issent to contact devices 70. In the present embodiment, the request issent as a push notification from application 202 on contact device 70,and is sent to a plurality of contacts which the wearer of the alertdevice 100 has selected via application 202 on mobile device 200. Thestatus check request message invites the contact to communicate with thedistressed individual by, for example, making a telephone call to theindividual. In the present embodiment, the alert device 100 causes themobile device 200 to send the status check request message by orderingthe mobile device 200 to do so via the first paired connection 151. Insome embodiments, the second paired connection 151 may be used toinitiate the status check request.

At block 406, it is determined whether a contact has responded to thestatus check request. For example, a contact device 70 may havetelephoned the distressed individual at mobile device 200. If a contacthas telephoned the distressed individual, and the wearer answers thecall, the call from the contact is received at block 408. The contactmay then render assistance to the distressed individual. Furthermore,having been contacted by a third party contact device 70, the mobiledevice 200 may send a cancel command to the alert device 100 to endmethod 400 so that further steps to initiate telephony are not takenwhere assistance has already been rendered. If no response has beenreceived, block 410 is executed.

At block 410, it is determined whether an expiry rule has beensatisfied. In the present embodiment, the expiry rule is determinationof whether a pre-determined length of time has elapsed during which noresponse to the status check request has been received. If the periodhas not elapsed, block 406 is executed again. If the pre-determinedlength of time has elapsed, it is identified that the expiry rule hasbeen satisfied, and block 412 is executed. For example, the expiry rulemay be satisfied upon lapsation of a countdown timer, for example if a2-minute countdown timer elapses before a response to the status checkrequest is received.

At block 412, after satisfaction of the expiry rule, the second pairedconnection 152 is made active to connect to the mobile device 200. Inembodiments in which the mobile device 200 is restricted from initiatingtelephony when in locked mode, such as an iOS device in locked or sleepmode, a low-power communications link such as BLE does not haveprivileged access to initiate telephony from the mobile device 200. Atelephony-enabled communication having hands-free profile capability,such as a BTC connection, however, does have privileged access toinitiate telephony from the mobile device 200 in locked mode.

At block 414, the alert device 100 causes the mobile device 200 to callan emergency service 62. In the example embodiment shown, the secondpaired connection 152, as a BTC link, allows the alert device 100, whichis master of the BTC link, to connect to the mobile device 200 in orderto initiate a telephone call to the emergency service 62. The wearer ofthe alert device 100 can then communicate through the mobile device 200to the emergency assistance.

In the present embodiment, at least blocks 402, 404, 410, 412, and 414are coded via firmware 160 into the alert device 100. Instructions forthese blocks being coded in firmware 160, rather than solely inapplication 202, is one way for the alert device 100 to alert thirdparties of a distress, even where application 202 is not activelyrunning on the mobile device 200. In other embodiments, including thosein which the application 202 is actively running on mobile device 200,any combination of blocks 402, 404, 406, 410, 412, and 414, may beperformed by the mobile device 200.

In some embodiments, firmware 160 may contain instructions forproceeding directly to blocks 412 and 414 for initiating a telephonecall via second paired connection 152 to an emergency service 62,without executing blocks 404 through 410, foregoing the status checkrequest procedure.

In still other embodiments, block 414 may comprise calling a selectedcontact from the contact devices 70 prior to, or in lieu of, making acall to an emergency service 62. In some of such embodiments, severalcalls may be made to several contact devices 70, prior to, or in lieuof, making a call to an emergency service 62.

FIG. 6 depicts mobile device 200 sending a status check request to acontact device 70, according to a non-limiting embodiment. FIG. 6 showsscreen captures of respective applications 202 running on devices 200,70, in communication over network 60.

After initiation of a status check request from mobile device 200,mobile device 200 displays a status check request user interface 202B.Interface 202B includes a cancel button 202B-1 for cancelling the statuscheck request, an emergency button 202B-2 for calling an emergencyservice 62 immediately, such as an emergency dispatch service, and acountdown timer display 202B-3 indicating a countdown time until anemergency service 62 will be called automatically. The alert device 100may additionally include a countdown timer (not shown) in firmware 160for determining whether to initiate telephony to emergency service 62.

After receipt of a status check request on contact device 70, contactdevice 70 displays a status check notification user interface 202C.Interface 202C includes close button 202C-1 for closing the interface202C, a call button 202C-2 for calling the mobile device 200 issuing thestatus check request, and a messaging interface 202C-3 for messaging themobile device 200 as a short message service (SMS) or as a directmessage through applications 202 running on respective devices 200, 70.

FIGS. 7A and 7B depict example embodiments in which the alert device 100is made into a wearable article. FIG. 7A is an assembly diagram of thealert device 100 being assembled into an article of jewelry 700,according to a non-limiting embodiment. The article of jewelry 700includes fascia portion 702 and pendant portion 704. In the presentembodiment, the alert device 100 is shaped such that fascia portion 702can be releasably coupled over the front chassis 112 of the alert device100 to attach with pendant portion 704 by a snap mechanism. The fasciaportion 702 provides ornamentation to the alert device 100.

The pendant portion 704 includes an opening 705 which thus allows therear chassis 110 of the alert device 100, and the peripheral componentssuch as the alert button 102, to be accessible through pendant portion704. In this way, the alert device 100 can be worn by loop 706 aroundthe neck of an individual, discreetly disguised as an article of jewelry700, with the alert button 102 on the alert device 100 out of sight, butreadily accessible, from opening 705 of the pendant portion 704, therear chassis 110 being oriented toward the individual. In the presentembodiment, the loop 706 includes a cord. In other embodiments, the loop706 may include a chain, string, or other flexible member wearablearound an individual's neck. In some embodiments, the loop 706 includesa chain having a clasp. In some embodiments, the clasp includes twomagnetic portions which are separable to unloop the chain. As a furtherexample, the clap may include two hemispheric magnetic portions attachedby clips to the chain.

Other embodiments in which the alert device 100 is assembled into awearable article are contemplated. For example, in other embodiments,the loop 706 may be on the fascia portion 702 to provide for wearingaround the neck of an individual. In other embodiments, the wearablearticle may enclose or partially enclose the alert device 100 whileallowing the alert device 100 to be worn with its alert button 102concealed.

FIG. 7B is an assembly diagram of the alert device 100 being assembledinto a wearable loop member 902, according to a non-limiting embodiment.The alert device 100 is shaped such it can be releasably coupled withloop member 902, which includes a loop 904 for wearing around anindividual's neck. In other embodiments, the alert device 100 may befastened, glued, or otherwise fixed into loop member 902.

FIG. 8 provides additional views of the alert device 100, and furtherindicating front chassis 112 and rear chassis 110.

FIG. 9 provides additional views of the article of jewelry 700, andfurther indicating fascia portion 702 and pendant portion 704.

FIG. 10 provides additional views of the alert 100 assembled into thearticle of jewelry 700, and further indicating fascia portion 702,pendant portion 704, loop 706, and the alert device 100 having alertbutton 102.

FIG. 11 provides additional views of the wearable loop member 902.

Thus, it can be seen from the above that an alert device can be providedas part of a low-power mobile telephony alert system. The alert deviceuses a low-power communication link to transmit status data from thealert device to the mobile device, and uses a telephony-enabledcommunication link to use the telephony capability of the mobile devicewhile the mobile device is in locked mode, thereby overcoming suchrestrictions against low-power communication links. When a triggerindicating that the individual is distressed occurs, the alert devicecan cause the mobile device to initiate a status check request to thirdparty contact devices, and can initiate telephony from the mobile deviceto an emergency service. The alert device can be made compact andincorporated into an article of jewelry or a wearable loop member fordiscrete wear.

In some embodiments, in place of telephony to an emergency service, anemergency service may be contacted by way of a Voice Over InternetProtocol (VOIP) call, a video call, text messaging, data calls, or othermeans of communication.

In some embodiments, the alert device and mobile device may be incommunication by means other than a BLE and BTC link, including Wi-Fi,near-field-communication (NFC), or other connection, which provides forcommunication between the two devices and which permits the alert deviceto cause the mobile device to make external communications to seekassistance from third parties.

In some embodiments, the alert device may be in communication withtelephony-enabled base station. In such embodiments, the alert devicemay be configured to initiate telephony from the telephony-enabled basestation to alert an emergency service. In some of such embodiments, thealert device may be in communication with the base station by radiofrequency (RF) or another long-range communication link.

In some embodiments, an indication that the individual is distressed canbe determined by additional triggers. For example, where the alertdevice includes a microphone or other sound recorder, a trigger may berecognized when particular sounds are detected. As another example, atrigger may be recognized where a maintenance button has not beenpressed for a pre-determined length of time. As another example, wherethe alert device includes a heartrate monitor, a trigger may berecognized where the wearer's heartrate drops below a threshold or risesabove a threshold. Similarly, where the alert device includes a bloodpressure sensor, a trigger may be recognized where the wearer's bloodpressure drops below a threshold or rises above a threshold.

In still other embodiments, the mobile device may comprise a smartphonethat may have telephony initiated by a low-power communication link suchas a BLE connection. In such embodiments, the mobile device may be incommunication with the alert device via a single communications link inwhich the alert device can cause the mobile device to initiate atelephone call or other communication to seek assistance.

In still other embodiments, the alert device may be incorporated into abracelet, watch, or other article to be worn on an individual's person.

The scope of the claims should not be limited by the embodiments setforth in the above examples, but should be given the broadestinterpretation consistent with the description as a whole.

1. An alert device for initiating telephony from a mobile device inlocked mode, the alert device comprising: a communication interfaceconfigured to: establish a first paired connection with the mobiledevice, the mobile device running a status data monitoring application,the first paired connection including a low-power communication linkhaving privileged access to the status data monitoring application forrecording status data from the alert device to the mobile device inlocked mode, the low-power communication link configured for continuouslow-energy transmission of status data from the alert device to thestatus data monitoring application; establish a second paired connectionwith the mobile device, the second paired connection including atelephony-enabled communication link having privileged access toinitiate telephony from the mobile device in locked mode, thetelephony-enabled communication link configured for initiating a VoiceOver Internet Protocol (VOIP) call from the mobile device in response torecognition of a trigger represented in the status data from the alertdevice; and transmit the status data from the alert device to the mobiledevice, via the first paired connection, for collection by the statusdata monitoring application; a memory storage unit for storingprogramming instructions and the status data; and a processor incommunication with the communication interface and memory storage unit,the processor configured to: recognize the trigger represented in thestatus data, and, responsive to recognition of the trigger, initiate,via one of the first paired connection and the second paired connection,a status check request from the mobile device to at least one thirdparty contact device, the status check request having an expiry rule;identify satisfaction of the expiry rule of the status check request,and, responsive to satisfaction of the expiry rule, connect to themobile device from locked mode via the second paired connection; andinitiate, via the second paired connection, telephony from the mobiledevice to a third-party emergency service.
 2. (canceled)
 3. The alertdevice of claim 1, wherein the alert device further comprises a motionsensor, wherein the status data comprises motion sensor data, andwherein the trigger comprises the status data indicating inactivity ofthe alert device for a pre-determined length of time.
 4. (canceled) 5.The alert device of claim 1, wherein the alert device further comprisesan alert button, and wherein the trigger comprises the status dataindicating a pressed state of the alert button.
 6. The alert device ofclaim 5, wherein the alert device comprises a wearable article having anopening for providing concealed access to the alert button of the alertdevice.
 7. The alert device of claim 6, wherein the wearable articlecomprises a fascia portion and a pendant portion releasably attachableto enclose the alert device, the fascia portion providing ornamentationto the alert device, and the pendant portion concealing the alert buttonand providing a loop for wearing the alert device.
 8. The alert deviceof claim 1, wherein the expiry rule comprises lapsation of a countdowntimer.
 9. A method for initiating telephony from a mobile device inlocked mode using an alert device, the method comprising: pairing thealert device with the mobile device via a first paired connection, themobile device running a status data monitoring application, the firstpaired connection including a low-power communication link havingprivileged access to the status data monitoring application forrecording status data from the alert device to the mobile device inlocked mode, the low-power communication link configured for continuouslow-energy transmission of status data from the alert device to thestatus data monitoring application; pairing the alert device with themobile device via a second paired connection, the second pairedconnection including a telephony-enabled communication link havingprivileged access to initiate telephony from the mobile device in lockedmode, the telephony-enabled communication link configured for initiatinga Voice Over Internet Protocol (VOIP) call from the mobile device inresponse to recognition of a trigger represented in the status data fromthe alert device; transmitting status data from the alert device to themobile device, via the first paired connection, for collection by thestatus data monitoring application; responsive to recognition of thetrigger represented in the status data, initiating, via one of the firstpaired connection and the second paired connection, a status checkrequest from the mobile device to at least one third party contactdevice, the status check request having an expiry rule; responsive tosatisfaction of the expiry rule of the status check request, connectingto the mobile device from locked mode via the second paired connection;and initiating, via the second paired connection, telephony from themobile device to a third-party emergency service.
 10. (canceled)
 11. Themethod of claim 9, wherein the expiry rule comprises lapsation of acountdown timer.
 12. The method of claim 9, wherein the status datacomprises motion sensor data from a motion sensor on the alert device,and wherein recognition of the trigger represented in the status datacomprises recognizing inactivity of the alert device for apre-determined length of time.
 13. (canceled)
 14. The method of claim 9,wherein the status data comprises pressed state data from an alertbutton on the alert device, and wherein recognition of the triggerrepresented in the status data comprises a pressed state of the alertbutton.
 15. A low-power mobile telephony alert system comprising: amobile device; at least one third party contact device; an emergencyservice; and an alert device for initiating telephony from the mobiledevice in locked mode to the emergency service, the alert devicecomprising: a communication interface configured to: establish a firstpaired connection with the mobile device, the mobile device running astatus data monitoring application, the first paired connectioncomprising a low-power communication link having privileged access tothe status data monitoring application for recording status data fromthe alert device to the mobile device in locked mode, the low-powercommunication link configured for continuous low-energy transmission ofstatus data from the alert device to the status data monitoringapplication; establish a second paired connection with the mobiledevice, the second paired connection comprising a telephony-enabledcommunication link having privileged access to initiate telephony fromthe mobile device in locked mode, the telephony-enabled communicationlink configured for initiating a Voice Over Internet Protocol (VOIP)call from the mobile device in response to recognition of a triggerrepresented in the status data from the alert device; and transmit thestatus data from the alert device to the mobile device, via the firstpaired connection, for collection by the status data monitoringapplication; a memory storage unit for storing programming instructionsand the status data; and a processor in communication with thecommunication interface and memory storage unit, the processorconfigured to: recognize the trigger represented in the status data,and, responsive to recognition of the trigger, initiate, via one of thefirst paired connection and the second paired connection, a status checkrequest from the mobile device to at least one third party contactdevice, the status check request having an expiry rule; identifysatisfaction of the expiry rule of the status check request, and,responsive to satisfaction of the expiry rule, connect to the mobiledevice from locked mode via the second paired connection; and initiate,via the second paired connection, telephony from the mobile device to anemergency service.
 16. (canceled)
 17. The system of claim 15, whereinthe alert device further comprises a motion sensor, wherein the statusdata comprises motion sensor data, and wherein the trigger comprises thestatus data indicating inactivity of the alert device for apre-determined length of time.
 18. (canceled)
 19. The system of claim15, wherein the alert device further comprises an alert button, andwherein the trigger comprises the status data indicating a pressed stateof the alert button.